From 991db4fc3fb590a0a8cb5746f25c71bd326d047c Mon Sep 17 00:00:00 2001 From: robertl Date: Wed, 29 Nov 2006 19:49:20 +0000 Subject: [PATCH] The first pass that marks up commands with and removes explicit linebreaking. More to follow. --- xmldoc/chapters/build.xml | 6 ++-- xmldoc/chapters/use.xml | 33 +++++++++--------- xmldoc/filters/arc.xml | 2 +- xmldoc/filters/discard.xml | 2 +- xmldoc/filters/duplicate.xml | 2 +- xmldoc/filters/interpolate.xml | 6 ++-- xmldoc/filters/nuketypes.xml | 2 +- xmldoc/filters/options/duplicate-all.xml | 2 +- xmldoc/filters/options/duplicate-correct.xml | 2 +- xmldoc/filters/options/track-merge.xml | 2 +- xmldoc/filters/options/track-move.xml | 2 +- xmldoc/filters/options/track-sdistance.xml | 14 ++++---- xmldoc/filters/options/track-split.xml | 22 +++++------- xmldoc/filters/options/track-start.xml | 2 +- xmldoc/filters/options/transform-del.xml | 5 +-- xmldoc/filters/options/transform-rte.xml | 3 +- xmldoc/filters/options/transform-trk.xml | 3 +- xmldoc/filters/options/transform-wpt.xml | 3 +- xmldoc/filters/polygon.xml | 6 ++-- xmldoc/filters/position.xml | 2 +- xmldoc/filters/radius.xml | 2 +- xmldoc/filters/simplify.xml | 2 +- xmldoc/filters/stack.xml | 36 ++++++++++---------- xmldoc/filters/transform.xml | 4 ++- xmldoc/formats/an1.xml | 2 +- xmldoc/formats/bcr.xml | 2 +- xmldoc/formats/garmin.xml | 8 ++--- xmldoc/formats/garmin_txt.xml | 2 +- xmldoc/formats/html.xml | 2 +- xmldoc/formats/igc.xml | 28 +++++++-------- xmldoc/formats/magnav.xml | 2 +- xmldoc/formats/mapconverter.xml | 2 +- xmldoc/formats/options/an1-nogc.xml | 2 +- xmldoc/formats/options/an1-road.xml | 2 +- xmldoc/formats/options/bcr-index.xml | 2 +- xmldoc/formats/options/compegps-index.xml | 2 +- xmldoc/formats/options/garmin-get_posn.xml | 2 +- xmldoc/formats/options/garmin-power_off.xml | 2 +- xmldoc/formats/options/igc-timeadj.xml | 4 +-- xmldoc/formats/options/ignrando-index.xml | 2 +- xmldoc/formats/options/nmn4-index.xml | 2 +- xmldoc/formats/options/stmsdf-index.xml | 4 +-- xmldoc/formats/options/stmwpp-index.xml | 2 +- xmldoc/formats/options/tiger-genurl.xml | 8 +++-- xmldoc/formats/palmdoc.xml | 2 +- xmldoc/formats/psp.xml | 2 +- xmldoc/formats/stmsdf.xml | 4 +-- xmldoc/formats/tef.xml | 2 +- xmldoc/formats/text.xml | 2 +- xmldoc/formats/wbt-bin.xml | 4 +-- xmldoc/formats/wbt.xml | 2 +- xmldoc/formats/xmapwpt.xml | 6 ++-- 52 files changed, 131 insertions(+), 140 deletions(-) diff --git a/xmldoc/chapters/build.xml b/xmldoc/chapters/build.xml index a4b2efb3f..c49cdbf0e 100644 --- a/xmldoc/chapters/build.xml +++ b/xmldoc/chapters/build.xml @@ -19,8 +19,8 @@ Linux, Solaris, and a variety of processors and compilers. In most cases, the code is as simple to build as running: - ./configure && make + ./configure && make Expat is strongly recommended for source builds as it is required for reading all the XML formats such as GPX. @@ -29,9 +29,11 @@ required for reading all the XML formats such as GPX. is recommended for OS/X and Linux if you want to use a USB Garmin. There are additional flags that can be passed to configure to - customize your build of GPSBabel. ./configure --help lists all the supported options, but additionally we have: + customize your build of GPSBabel. +./configure --help +lists all the supported options, but additionally we have: Excludes the shapefile support. diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml index 4b7a444dc..21b81bc39 100644 --- a/xmldoc/chapters/use.xml +++ b/xmldoc/chapters/use.xml @@ -33,7 +33,7 @@ options you need to know to do those things: The format parameters in the above list refer to the names of formats or file types supported by GPSBabel. -gpsbabel -? +gpsbabel -? will always show you the supported file types. In this document, the various supported formats are listed in . The name that you would use on the command line follows the format name in @@ -53,15 +53,15 @@ name of a file to be read or written. this program, just tell it what you're reading, where to read it from, what you're writing, and what to write it to. For example: - gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx + gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx tells it to read the file "/tmp/geocaching.loc" in geocaching.com format and create a new file in GPX format. This command will read from a Magellan unit attached to the first serial port on a Linux system (device names will vary on other OSes) and write them as a geocaching loc file. The second command does the same on Microsoft Windows. - gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc - gpsbabel -i magellan -f com1 -o geo -F mag.loc + gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc + gpsbabel -i magellan -f com1 -o geo -F mag.loc Optionally, you may specify "-s" in any command line. This causes the program to ignore any "short" names that may be present in the source data format and synthesize one from the @@ -73,8 +73,8 @@ name of a file to be read or written. the 'GC1234' ones that are optimized for NMEA-only receivers. A geocacher with a Magellan receiver may thus find commands like this useful. - gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0 - gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1 + gpsbabel -s -i geo -f geocaching.loc -o magellan -F /dev/ttyS0 + gpsbabel -s -i geo -f geocaching.loc -o magellan -F com1 Suboptions @@ -89,7 +89,7 @@ name of a file to be read or written. itself. The available suboptions are listed on the individual format pages. We'll make an example from : - gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml + gpsbabel -i gpx -f file.gpx -o kml,deficon="file://myicon.png",lines=0 -F one.kml -o kml -F two.kml This command will read the GPX file file.gpx and create two KML files. one.kml will @@ -124,19 +124,18 @@ merged data to multiple destinations. -i argument is seen. Files are read in the order they appear. So you could merge three input files into one output file with: - gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc + gpsbabel -i geo -f 1.loc -f 2.loc -f 3.loc -o geo -F big.loc You can merge files of different types: - gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx \ --o gpsutil -F big.gps + gpsbabel -i geo -f 1.loc -i gpx -f 2.gpx -i pcx 3.pcx +-o gpsutil -F big.gps You can write the same data in different output formats: - gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt + gpsbabel -i geo -f 1.loc -o gpx -F 1.gpx -o pcx 1.wpt If you want to change the character set of input or/and output side you can do this with the option . You can get a complete list of supported character sets with "gpsbabel -l". To change the character set on both sides you should do this: - gpsbabel -i xcsv,style=foo.style -c latin1 -f foo \ - -o xcsv,style=bar.style -c ms-ansi -F bar + gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar Note, that some formats has a fixed character set and ignore this option. @@ -149,7 +148,7 @@ merged data to multiple destinations. waypoints, and is the default. So if you wanted to read all data from your unit into a gpx file, you might use a command like: - gpsbabel -t -r -w -i magellan -f com1: -o gpx -F backup.gpx + gpsbabel -t -r -w -i magellan -f com1: -o gpx -F backup.gpx Tracks and routes are advanced features and don't try to handle every possible hazard that can be encountered during a conversion. If you're merging or converting files @@ -254,7 +253,7 @@ merged data to multiple destinations. (i.e. wrapper applications using GPSBabel in the background). The inifile mechanism can be disabled with an empty filename. - gpsbabel -p "" -i gpx -f something.gpx -o tiger -F - + gpsbabel -p "" -i gpx -f something.gpx -o tiger -F - Realtime tracking @@ -266,8 +265,8 @@ merged data to multiple destinations. inputs and KML is supported on output. Additional formats may be added by interested parties later. + gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml - gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml Will read the USB-connected Garmin and rewrite 'xxx.kml' atomically, suitable for a self-refreshing network link in Google Earth. @@ -287,8 +286,8 @@ merged data to multiple destinations. Here is an example demonstrating segmenting a large command line by placing the input and filtering directives in a file called 'all_my_files'. - gpsbabel -b all_my_files -o gdb -F all_my_tracks.gdb + gpsbabel -b all_my_files -o gdb -F all_my_tracks.gdb 'all_my_files' could look like this: diff --git a/xmldoc/filters/arc.xml b/xmldoc/filters/arc.xml index e3a032dc6..12aa7ae1b 100644 --- a/xmldoc/filters/arc.xml +++ b/xmldoc/filters/arc.xml @@ -37,6 +37,6 @@ Assuming the arc above is in a file called would include only points within one mile of the section of Lima Road covered by the arc. -gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt +gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt diff --git a/xmldoc/filters/discard.xml b/xmldoc/filters/discard.xml index 962549f65..09fdb4159 100644 --- a/xmldoc/filters/discard.xml +++ b/xmldoc/filters/discard.xml @@ -6,7 +6,7 @@ for a given configuration of GPS satellites. Using the discard filter - gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx + gpsbabel -i gpx -f in.gpx -x discard,hdop=10,vdop=20,hdopandvdop -o gpx -F out.gpx Contributed by Tobias Minich. diff --git a/xmldoc/filters/duplicate.xml b/xmldoc/filters/duplicate.xml index 79b85af9d..450d9ed29 100644 --- a/xmldoc/filters/duplicate.xml +++ b/xmldoc/filters/duplicate.xml @@ -15,6 +15,6 @@ Generally, at least one of these options is required. gpx file that more than likely contains only unique points and point data. - gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx + gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx diff --git a/xmldoc/filters/interpolate.xml b/xmldoc/filters/interpolate.xml index 2b08aec0a..453311ec3 100644 --- a/xmldoc/filters/interpolate.xml +++ b/xmldoc/filters/interpolate.xml @@ -12,19 +12,19 @@ must specify either the This command line reads track.gpx and inserts points wherever two adjacent trackpoints are more than 10 seconds apart: -gpsbabel -i gpx -f track.gpx -x interpolate,time=10 -o gpx -F newtrack.gpx +gpsbabel -i gpx -f track.gpx -x interpolate,time=10 -o gpx -F newtrack.gpx This command reads track.gpx and inserts points wherever two adjacent trackpoints are more than 15 kilometers apart: -gpsbabel -i gpx -f track.gpx -x interpolate,distance=15k -o gpx -F newtrack.gpx +gpsbabel -i gpx -f track.gpx -x interpolate,distance=15k -o gpx -F newtrack.gpx This command reads track.gpx and inserts points wherever two adjacent trackpoints are more than 2 miles apart: -gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx +gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx diff --git a/xmldoc/filters/nuketypes.xml b/xmldoc/filters/nuketypes.xml index 824f20d56..839760851 100644 --- a/xmldoc/filters/nuketypes.xml +++ b/xmldoc/filters/nuketypes.xml @@ -11,6 +11,6 @@ waypoints and you want a GPX file that contains only tracks, you may use this filter to remove the waypoints and the routes with this command: -gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx +gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx diff --git a/xmldoc/filters/options/duplicate-all.xml b/xmldoc/filters/options/duplicate-all.xml index 582a64b28..c85ec5b00 100644 --- a/xmldoc/filters/options/duplicate-all.xml +++ b/xmldoc/filters/options/duplicate-all.xml @@ -12,6 +12,6 @@ This option may be used to implement an "ignore list." In the following example, the duplicate filter is used to remove a list of waypoints to be ignored from a larger collection of waypoints: -gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx +gpsbabel -i gpx -f waypoints.gpx -i csv -f to_ignore.csv -x duplicate,shortname,all -o gpx -F filtered.gpx diff --git a/xmldoc/filters/options/duplicate-correct.xml b/xmldoc/filters/options/duplicate-correct.xml index 20741d15b..b66b6e90b 100644 --- a/xmldoc/filters/options/duplicate-correct.xml +++ b/xmldoc/filters/options/duplicate-correct.xml @@ -11,7 +11,7 @@ geocaches in a Groundspeak pocket query: Using the duplicate filter to correct the locations of "puzzle" geocaches -gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx +gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx After this command is run, the waypoints in the output file will have all of the descriptive information from 43622.gpx, but diff --git a/xmldoc/filters/options/track-merge.xml b/xmldoc/filters/options/track-merge.xml index 5ca5bbbf9..6d2e0d2a9 100644 --- a/xmldoc/filters/options/track-merge.xml +++ b/xmldoc/filters/options/track-merge.xml @@ -9,6 +9,6 @@ dropped. Suppose you want to merge tracks recorded with two different GPS devices at the same time. To do that, use this command line: -gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx +gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx diff --git a/xmldoc/filters/options/track-move.xml b/xmldoc/filters/options/track-move.xml index 0641de1e9..6ba10c0ce 100644 --- a/xmldoc/filters/options/track-move.xml +++ b/xmldoc/filters/options/track-move.xml @@ -8,6 +8,6 @@ time zone. The following command line will shift all tracks to be one hour later. -gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx +gpsbabel -t -i gpx -f in.gpx -x track,move=+1h -o gpx -F out.gpx diff --git a/xmldoc/filters/options/track-sdistance.xml b/xmldoc/filters/options/track-sdistance.xml index 7fc4db8f5..35313095d 100644 --- a/xmldoc/filters/options/track-sdistance.xml +++ b/xmldoc/filters/options/track-sdistance.xml @@ -10,12 +10,12 @@ For example, to split the track if the distance between points is greater than 100 meters, use this: - -gpsbabel -t \ - -i gpx -f in.gpx \ - -x track,pack,sdistance=0.1k" \ + +gpsbabel -t + -i gpx -f in.gpx + -x track,pack,sdistance=0.1k" -o gpx -F out.gpx - + The sdistance option can be combined with the split option. The track then will be split only if both time and distance interval exceeds the supplied values. This technique can be used to @@ -26,11 +26,11 @@ gpsbabel -t \ This example splits the track if the device is without signal for at least 5 minutes and during this time moves more than 300 meters: - + gpsbabel -t \ -i gpx -f in.gpx \ -x track,pack,sdistance=0.3k,split=5m \ -o gpx -F out.gpx - + diff --git a/xmldoc/filters/options/track-split.xml b/xmldoc/filters/options/track-split.xml index 00af234b5..8f93ff155 100644 --- a/xmldoc/filters/options/track-split.xml +++ b/xmldoc/filters/options/track-split.xml @@ -4,16 +4,12 @@ split a single tracks into separate tracks for each day and name them, use this: - -gpsbabel -t -i gpx -f in.gpx -x \ - track,split,title="ACTIVE LOG \ - # %Y%m%d" -o gpx -F out.gpx + gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx If the input has multiple tracks, pack them together before splitting them back apart per day thusly: - -gpsbabel -t -i gpx -f in.gpx \ - -x track,pack,split,title="ACTIVE LOG # %D" \ - -o gpx -F out.gpx + gpsbabel -t -i gpx -f in.gpx + -x track,pack,split,title="ACTIVE LOG # %D" + -o gpx -F out.gpx Additionally you can add an interval to the split option. With this the track will be split if the time between two points is greater than this parameter. The @@ -24,9 +20,9 @@ gpsbabel -t -i gpx -f in.gpx \ For example, to split a track based on an four hour interval, use this: - -gpsbabel -t \ - -i gpx -f in.gpx \ - -x track,pack,split=4h,title="LOG # %c" \ + +gpsbabel -t + -i gpx -f in.gpx + -x track,pack,split=4h,title="LOG # %c" -o gpx -F out.gpx - + diff --git a/xmldoc/filters/options/track-start.xml b/xmldoc/filters/options/track-start.xml index 9df4086fd..06c22ccb2 100644 --- a/xmldoc/filters/options/track-start.xml +++ b/xmldoc/filters/options/track-start.xml @@ -20,5 +20,5 @@ given date, you need not specify the minutes or seconds. To get only the parts of a track that were mapped on 20 July 2005 between 10 AM and 6 PM, use this command line: -gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx +gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx diff --git a/xmldoc/filters/options/transform-del.xml b/xmldoc/filters/options/transform-del.xml index c6d8b694b..9aa4e47da 100644 --- a/xmldoc/filters/options/transform-del.xml +++ b/xmldoc/filters/options/transform-del.xml @@ -5,8 +5,5 @@ you are trying to avoid duplicated data in the output. Convert a GPX track to GPX waypoints, tossing the original track - -gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del \ --o gpx -F converted.gpx - +gpsbabel -i gpx -f blah.gpx -x transform,wpt=trk,del -o gpx -F converted.gpx diff --git a/xmldoc/filters/options/transform-rte.xml b/xmldoc/filters/options/transform-rte.xml index ba8178301..631ec4251 100644 --- a/xmldoc/filters/options/transform-rte.xml +++ b/xmldoc/filters/options/transform-rte.xml @@ -6,7 +6,6 @@ This option selects the destination type of this filter to be routes. Choose th Say you you have a data file that came from CSV file that you want to convert to a GPX route that can be loaded into Mapsource. Use the following command: -gpsbabel -i csv -f blah.txt -x transform,rte=wpt \ --o gdb -F blah.gdb +gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb diff --git a/xmldoc/filters/options/transform-trk.xml b/xmldoc/filters/options/transform-trk.xml index 492a1fb23..8a72a27b5 100644 --- a/xmldoc/filters/options/transform-trk.xml +++ b/xmldoc/filters/options/transform-trk.xml @@ -8,7 +8,6 @@ A single track will be created in the sequence they appear in the input. Say you you have a data file that came from CSV file that you want to convert to a GPX track that can be loaded into Mapsource. Use the following command: -gpsbabel -i csv -f blah.txt -x transform,trk=wpt \ --o gdb -F blah.gdb +gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb diff --git a/xmldoc/filters/options/transform-wpt.xml b/xmldoc/filters/options/transform-wpt.xml index 0889e9a9b..1399f0fb0 100644 --- a/xmldoc/filters/options/transform-wpt.xml +++ b/xmldoc/filters/options/transform-wpt.xml @@ -6,7 +6,6 @@ Choose this when you want to convert tracks or routes into waypoints. Converting a track to a sequence of waypoints Say you you have a KML file that contains a track but you want to convert it to a CSV file that can contain only waypoints, perhaps to import into a spreadsheet. Use the following command: -gpsbabel -i kml -f blah.kml -x transform,wpt=trk \ --o csv -F blah.txt +gpsbabel -i kml -f blah.kml -x transform,wpt=trk -o csv -F blah.txt diff --git a/xmldoc/filters/polygon.xml b/xmldoc/filters/polygon.xml index a193f903e..5b5bb63cf 100644 --- a/xmldoc/filters/polygon.xml +++ b/xmldoc/filters/polygon.xml @@ -48,7 +48,7 @@ Suppose you have a polygon file that defines the border of your county, called mycounty.txt. This command line will give you only the points in your county: -gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt +gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt Using the polygon and arc filters to find points in or nearly in a @@ -61,11 +61,11 @@ boundaries of your polygon are not quite perfect, so you want to provide a buffer zone around it in case there are points nearby that should be in the polygon but aren't quite. </para> -<screen> +<para><command> gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt -x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append -x duplicate,shortname -o gpx -F nearmycounty.gpx -</screen> +</command></para> <para> This command makes a copy of the points, finds the ones that are in your your county, swaps that result with the copy of the original set of points, diff --git a/xmldoc/filters/position.xml b/xmldoc/filters/position.xml index 13ff374a0..4bf0869c1 100644 --- a/xmldoc/filters/position.xml +++ b/xmldoc/filters/position.xml @@ -10,6 +10,6 @@ has come before. The following command removes multiple points that are within one foot of each other, leaving just one. </para> -<screen format="linespecific">gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</screen> +<para><command>gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</command></para> </example> diff --git a/xmldoc/filters/radius.xml b/xmldoc/filters/radius.xml index cdc970f40..607f97e59 100644 --- a/xmldoc/filters/radius.xml +++ b/xmldoc/filters/radius.xml @@ -12,6 +12,6 @@ center appear earlier in the output file. <para>This example command line would include only points within 1 1/2 miles of N30.000 W 90.000</para> -<screen format="linespecific">gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</screen> +<para><command>gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</command></para> </example> diff --git a/xmldoc/filters/simplify.xml b/xmldoc/filters/simplify.xml index 976f61901..1c6f47938 100644 --- a/xmldoc/filters/simplify.xml +++ b/xmldoc/filters/simplify.xml @@ -17,5 +17,5 @@ For example, suppose you have a route from Street Atlas 2003 that you wish to use with a Magellan GPS receiver that only supports up to 50 points in a route: </para> -<screen format="linespecific">gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan -F grocery.rte</screen> +<para><command>gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan -F grocery.rte</command></para> diff --git a/xmldoc/filters/stack.xml b/xmldoc/filters/stack.xml index 45934ad15..40d30e75f 100644 --- a/xmldoc/filters/stack.xml +++ b/xmldoc/filters/stack.xml @@ -21,29 +21,29 @@ can fit in your computer's memory. duplicates can be removed with the DUPLICATE filter; see above.) </para> - <screen format="linespecific"> -gpsbabel -i gpx -f in.gpx \ - -x stack,push,copy \ - -x polygon,file=county_a.txt \ - -x stack,swap \ - -x polygon,file=county_b.txt \ - -x stack,pop,append \ + <para><command> +gpsbabel -i gpx -f in.gpx + -x stack,push,copy + -x polygon,file=county_a.txt + -x stack,swap + -x polygon,file=county_b.txt + -x stack,pop,append -o gpx -F out.gpx -</screen> +</command></para> <para> This example reads a large list of waypoints and extracts the points within 20 miles of each of two cities, writing the waypoint descriptions into two different PalmDoc files and exporting all of the points to the GPS receiver: </para> - <screen format="linespecific"> -gpsbabel -i gpx -f indiana.gpx \ - -x stack,push,copy \ - -x radius,lat=41.0765,lon=-85.1365,distance=20m \ - -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb \ - -x stack,swap \ - -x radius,lat=39.7733,lon=-86.1433,distance=20m \ - -o palmdoc,dbname=Indianapolis -F indianapolis.pdb \ - -x stack,pop,append \ + <para><command> +gpsbabel -i gpx -f indiana.gpx + -x stack,push,copy + -x radius,lat=41.0765,lon=-85.1365,distance=20m + -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb + -x stack,swap + -x radius,lat=39.7733,lon=-86.1433,distance=20m + -o palmdoc,dbname=Indianapolis -F indianapolis.pdb + -x stack,pop,append -o magellan -F fwaind.wpt -</screen> +</command></para> diff --git a/xmldoc/filters/transform.xml b/xmldoc/filters/transform.xml index 87a87d2e0..7a55f3e91 100644 --- a/xmldoc/filters/transform.xml +++ b/xmldoc/filters/transform.xml @@ -9,7 +9,9 @@ </para> <para> The following example show you how to create a route from a waypoint table. - <screen format="linespecific">gpsbabel -i csv waypts.txt -x transform,rte=wpt -o gpx -F route.gpx</screen> +</para> + <para><command>gpsbabel -i csv waypts.txt -x transform,rte=wpt -o gpx -F route.gpx</command></para> +<para> Only the first letter of option value decides which transformation will be done. Depending on the used option it can be only 'W' for waypoints, 'R' for routes or 'T' for tracks. diff --git a/xmldoc/formats/an1.xml b/xmldoc/formats/an1.xml index 81475ed2d..466fb5cd3 100644 --- a/xmldoc/formats/an1.xml +++ b/xmldoc/formats/an1.xml @@ -7,7 +7,7 @@ thick red lines for routes or tracks. It is possible to merge two drawing layers by doing something like this: </para> -<screen format="linespecific">gpsbabel -i an1 -f one.an1 -f two.an1 -o an1 -F merged.an1</screen> +<para><command>gpsbabel -i an1 -f one.an1 -f two.an1 -o an1 -F merged.an1</command></para> <para> In this case, the merged data will contain all of the diff --git a/xmldoc/formats/bcr.xml b/xmldoc/formats/bcr.xml index c5604099d..1542994c3 100644 --- a/xmldoc/formats/bcr.xml +++ b/xmldoc/formats/bcr.xml @@ -16,6 +16,6 @@ reports are welcome. </para> <example id="sample_bcr_command"> <title>Sample BCR command with all options - gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr + gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml index b72031f94..fbdf33fb1 100644 --- a/xmldoc/formats/garmin.xml +++ b/xmldoc/formats/garmin.xml @@ -121,10 +121,10 @@ To communicate via USB use "usb:" as the filename on all OSes. Thus, to read the waypoints from a Garmin USB unit and write them to a GPX file: + - gpsbabel -i garmin -f usb: -o gpx -F blah.gpx + gpsbabel -i garmin -f usb: -o gpx -F blah.gpx - If you have multiple units attached via USB, you may provide a unit number, with zero being the implied default. So if you @@ -132,7 +132,7 @@ "usb:0", "usb:1", and "usb:2". To get a list of recognized devices, specifiy a negative number such as: - gpsbabel -i garmin -f usb:-1 + gpsbabel -i garmin -f usb:-1 When reporting problems with the Garmin format, be sure to include @@ -140,7 +140,7 @@ the full unit model, firmware version, and be prepared to offer debugging dumps by adding "-D9" to the command line, like: - gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx + gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx Custom icons are supported on units that support that. diff --git a/xmldoc/formats/garmin_txt.xml b/xmldoc/formats/garmin_txt.xml index 54a391db1..06288ceef 100644 --- a/xmldoc/formats/garmin_txt.xml +++ b/xmldoc/formats/garmin_txt.xml @@ -18,6 +18,6 @@ be solved with the 'date' and 'time' options. Command showing garmin_txt output with all options - gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt + gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt diff --git a/xmldoc/formats/html.xml b/xmldoc/formats/html.xml index 1735a6b3d..0589fabad 100644 --- a/xmldoc/formats/html.xml +++ b/xmldoc/formats/html.xml @@ -12,5 +12,5 @@ for Geocachers with pocket queries. Groundspeak extensions and writes an HTML file with encrypted hints that is rendered using a custom stylesheet: -gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html +gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html diff --git a/xmldoc/formats/igc.xml b/xmldoc/formats/igc.xml index 0c1485b6e..8a900efd3 100644 --- a/xmldoc/formats/igc.xml +++ b/xmldoc/formats/igc.xml @@ -42,7 +42,7 @@ will not be accepted as proof of a flight. A track stored in another format (GPX for example) representing a recorded flight can be converted into an IGC file: -gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc +gpsbabel -i gpx -f mytrk.gpx -o igc -F myflight.igc If multiple track segments are provided in the input file, the one with the most points will be used. @@ -51,34 +51,34 @@ most points will be used. A route stored in another format representing a task declaration can be converted into an IGC file: -gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc +gpsbabel -i gpx -f myrte.gpx -o igc -F mytask.igc A route and a track in other formats can be included into a single IGC file: -gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc +gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -o igc -F myflight.igc A similar result can be obtained by downloading the track log and routes directly from a GPS device connected to a PC. For example to create an IGC file from data recorded in a Garmin GPS connected to the first serial port of a PC running Linux: -gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc +gpsbabel -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc For Windows operating systems: -gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc +gpsbabel -t -r -i garmin -f com1 -o igc -F myflight.igc A waypoint file in another format containing a waypoint whose short name is "PILOT" can be merged into an IGC file. The description field of the waypoint will be used for the pilot name in the IGC file header: -gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc -gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc +gpsbabel -i gpx -f mytrk.gpx -f myrte.gpx -f mywpt.gpx -o igc -F myflight.igc +gpsbabel -w -t -r -i garmin -f /dev/ttyS0 -o igc -F myflight.igc Some formats such as GPX allow routes, tracks and waypoints to exist in the same file and can be used to fully populate an IGC file: -gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc +gpsbabel -i gpx -f myall.gpx -o igc -F myflight.igc
@@ -88,11 +88,11 @@ Data in an IGC file can be converted into other formats. For example to generate OziExplorer files containing tracks representing the recorded flight (myozi.plt) and routes representing declared tasks (myozi.rte): -gpsbabel -i igc -f myflight.igc -o ozi -F myozi +gpsbabel -i igc -f myflight.igc -o ozi -F myozi Or to GPX format: -gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx +gpsbabel -i igc -f myflight.igc -o gpx -F myflight.gpx Header information from the IGC file will be written to the description field of the track(s). @@ -110,23 +110,23 @@ tracks. The latitude, longitude and timestamps in the tracks will be identical. A route stored in another format can be merged with an existing IGC file that has no task declaration, to generate a new IGC file with a task declaration: -gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc +gpsbabel -i igc -f myflight.igc -i gpx -f myrte.gpx -o igc -F mynew.igc A two dimensional (lat/lon) track recorded during a flight by a GPS receiver can be merged with a one dimensional (altitude) track recorded during the same flight by a barograph instrument. The result is a three dimensional IGC file representing the flight: -gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc +gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc The same can be acheived by downloading directly from a barograph instrument supported by GPSBabel. For example with a Brauniger IQ Comp GPS variometer: -gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc +gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc or: -gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc +gpsbabel -i baroiq -f com1 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc (Documentation contributed by Chris Jones, Aug 2004) diff --git a/xmldoc/formats/magnav.xml b/xmldoc/formats/magnav.xml index d2db2020f..b7ddeed08 100644 --- a/xmldoc/formats/magnav.xml +++ b/xmldoc/formats/magnav.xml @@ -27,7 +27,7 @@ PalmOS, not of NAV Companion.) To merge the databases, use a command line like the following: -gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb +gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb Second, you must use the installer to install your new PDB file. Don't make the mistake of copying it over the existing Companion_Waypoints.PDB diff --git a/xmldoc/formats/mapconverter.xml b/xmldoc/formats/mapconverter.xml index 1ab390cea..3531af7c4 100644 --- a/xmldoc/formats/mapconverter.xml +++ b/xmldoc/formats/mapconverter.xml @@ -14,7 +14,7 @@ The steps for using GPSBabel and Mapconverter go something like this: Step 1: Create a mapconverter file using gpsbabel. -gpsbabel -i geo -f geocaching.loc -o mapconverter -F foo.txt +gpsbabel -i geo -f geocaching.loc -o mapconverter -F foo.txt Step 2: Launch mapconverter.exe and choose foo.txt as your input file. Click the begin button to have mapconverter process foo.txt. diff --git a/xmldoc/formats/options/an1-nogc.xml b/xmldoc/formats/options/an1-nogc.xml index bdeb9dc1b..e2c9288a0 100644 --- a/xmldoc/formats/options/an1-nogc.xml +++ b/xmldoc/formats/options/an1-nogc.xml @@ -4,5 +4,5 @@ difficulty and terrain, GPSBabel will automatically include that information in the waypoint descriptions in the generated drawing file. If you do not want that, specify the "nogc" option on the command line: -gpsbabel -i gpx -f 12345.gpx -o an1,nogc -F 12345.an1 +gpsbabel -i gpx -f 12345.gpx -o an1,nogc -F 12345.an1 diff --git a/xmldoc/formats/options/an1-road.xml b/xmldoc/formats/options/an1-road.xml index f71a23181..1c32d7e71 100644 --- a/xmldoc/formats/options/an1-road.xml +++ b/xmldoc/formats/options/an1-road.xml @@ -59,7 +59,7 @@ local roads, but may be edited with the drawing tools in Street Atlas. This option has a special format that is best demonstrated by example: -"road=I-599!limited!Beecher St.!major" + "road=I-599!limited!Beecher St.!major" This option will cause any road named "I-599" to become a limited-access diff --git a/xmldoc/formats/options/bcr-index.xml b/xmldoc/formats/options/bcr-index.xml index 2d981b38b..164412e05 100644 --- a/xmldoc/formats/options/bcr-index.xml +++ b/xmldoc/formats/options/bcr-index.xml @@ -5,5 +5,5 @@ routes read from a more expressive format. If you have, say, a gpx file that contains two routes, you may use this option to write them one at a time to individual files. -gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr +gpsbabel -i gpx -f routes.gpx -o bcr,index=1 -F route1.bcr -o bcr,index=2 -F route2.bcr diff --git a/xmldoc/formats/options/compegps-index.xml b/xmldoc/formats/options/compegps-index.xml index dfccba67e..915db8f7e 100644 --- a/xmldoc/formats/options/compegps-index.xml +++ b/xmldoc/formats/options/compegps-index.xml @@ -5,4 +5,4 @@ tracks read from a more expressive format. If you have, say, a gpx file that contains two routes, you may use this option to write them one at a time to individual files. -gpsbabel -i gpx -f routes.gpx -o compegps,index=1 -F route1.txt -o compegps,index=2 -F route2.txt +gpsbabel -i gpx -f routes.gpx -o compegps,index=1 -F route1.txt -o compegps,index=2 -F route2.txt diff --git a/xmldoc/formats/options/garmin-get_posn.xml b/xmldoc/formats/options/garmin-get_posn.xml index a7720047c..7d93bab7f 100644 --- a/xmldoc/formats/options/garmin-get_posn.xml +++ b/xmldoc/formats/options/garmin-get_posn.xml @@ -1,5 +1,5 @@ This options gets the current longtitude and latitude from the attached GPS device and returns it as a single waypoint for further processing. For example, to return the current position from a USB Garmin to a KML file: -gpsbabel -i garmin,get_posn -f usb: -o kml -F myposition.kml +gpsbabel -i garmin,get_posn -f usb: -o kml -F myposition.kml diff --git a/xmldoc/formats/options/garmin-power_off.xml b/xmldoc/formats/options/garmin-power_off.xml index 63c22850d..145e7cf7a 100644 --- a/xmldoc/formats/options/garmin-power_off.xml +++ b/xmldoc/formats/options/garmin-power_off.xml @@ -4,5 +4,5 @@ Obviously, further processing once you have sent a "power off" command to a unit that supports it is rather futile, so place this option carefully in your command. -gpsbabel -o garmin,power_off -F /dev/ttyS0 +gpsbabel -o garmin,power_off -F /dev/ttyS0 diff --git a/xmldoc/formats/options/igc-timeadj.xml b/xmldoc/formats/options/igc-timeadj.xml index 2d6def3c8..ceeb749ca 100644 --- a/xmldoc/formats/options/igc-timeadj.xml +++ b/xmldoc/formats/options/igc-timeadj.xml @@ -5,12 +5,12 @@ not correlating correctly. This can be corrected manually by passing the time difference in seconds between the two time domains through the "timeadj" parameter. This can be any positive or negative integer: -gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc +gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=27 -F my3D.igc GPSBabel can also attempt to deduce the time difference automatically. This is done by comparing the time that it thinks that you landed on the GPS track and the barograph and adjusting accordingly: -gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc +gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc diff --git a/xmldoc/formats/options/ignrando-index.xml b/xmldoc/formats/options/ignrando-index.xml index 42c8f4e6f..fb06f1d79 100644 --- a/xmldoc/formats/options/ignrando-index.xml +++ b/xmldoc/formats/options/ignrando-index.xml @@ -5,5 +5,5 @@ tracks read from a more expressive format. If you have, say, a gpx file that contains two tracks, you may use this option to write them one at a time to individual files. -gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt +gpsbabel -i gpx -f tracks.gpx -o ignrando,index=1 -F track1.txt -o ignrando,index=2 -F track2.txt diff --git a/xmldoc/formats/options/nmn4-index.xml b/xmldoc/formats/options/nmn4-index.xml index 8b7f0c4f0..25aacb215 100644 --- a/xmldoc/formats/options/nmn4-index.xml +++ b/xmldoc/formats/options/nmn4-index.xml @@ -5,5 +5,5 @@ routes read from a more expressive format. If you have, say, a gpx file that contains two routes, you may use this option to write them one at a time to individual files. -gpsbabel -i gpx -f routes.gpx -o nmn4,index=1 -F route1.rte -o nmn4,index=2 -F route2.rte +gpsbabel -i gpx -f routes.gpx -o nmn4,index=1 -F route1.rte -o nmn4,index=2 -F route2.rte diff --git a/xmldoc/formats/options/stmsdf-index.xml b/xmldoc/formats/options/stmsdf-index.xml index 301d55b1f..1318ee775 100644 --- a/xmldoc/formats/options/stmsdf-index.xml +++ b/xmldoc/formats/options/stmsdf-index.xml @@ -11,7 +11,5 @@ This example will convert route number two and three into separate sdf files: - - gpsbabel -i gdb -f routes.gdb -r -o stmsdf,index=2 -F route-one.sdf -r -o stmsdf,index=3 -F route-three.sdf - + gpsbabel -i gdb -f routes.gdb -r -o stmsdf,index=2 -F route-one.sdf -r -o stmsdf,index=3 -F route-three.sdf diff --git a/xmldoc/formats/options/stmwpp-index.xml b/xmldoc/formats/options/stmwpp-index.xml index 6187a66a8..00ddb54b6 100644 --- a/xmldoc/formats/options/stmwpp-index.xml +++ b/xmldoc/formats/options/stmwpp-index.xml @@ -5,5 +5,5 @@ tracks read from a more expressive format. If you have, say, a gpx file that contains three routes, you may use this option to write them one at a time to individual files. -gpsbabel -i gpx -f routes.gpx -o stmwpp,index=1 -F route1.txt -o stmwpp,index=2 -F route2.txt -o stmwpp,index=3 -F route3.txt +gpsbabel -i gpx -f routes.gpx -o stmwpp,index=1 -F route1.txt -o stmwpp,index=2 -F route2.txt -o stmwpp,index=3 -F route3.txt diff --git a/xmldoc/formats/options/tiger-genurl.xml b/xmldoc/formats/options/tiger-genurl.xml index d1bd24f2b..093598a88 100644 --- a/xmldoc/formats/options/tiger-genurl.xml +++ b/xmldoc/formats/options/tiger-genurl.xml @@ -5,10 +5,12 @@ height, and width parameters in a form suitable for use in the URL to generate a map that will hold all the points to be displayed and is suitably scaled and centered. -For example: -gpsbabel -i geo -f geocaching.loc -o tiger,genurl=tiger.ctr -F tiger.dat +For example: +gpsbabel -i geo -f geocaching.loc -o tiger,genurl=tiger.ctr -F tiger.dat + may create tiger.ctr with -lat=36.042108&lon=-86.877408&ht=0.161172&wid=0.591771&iwd=768&iht=768 + +lat=36.042108&lon=-86.877408&ht=0.161172&wid=0.591771&iwd=768&iht=768 After uploading tiger.dat to a public server, a request to http://tiger.census.gov/cgi-bin/mapgen?murl=$THATFILE$(cat tiger.ctr) diff --git a/xmldoc/formats/palmdoc.xml b/xmldoc/formats/palmdoc.xml index 5c7a6cf31..a20dc0617 100644 --- a/xmldoc/formats/palmdoc.xml +++ b/xmldoc/formats/palmdoc.xml @@ -9,5 +9,5 @@ to a particular waypoint. The following command line reads a GPX file with Groundspeak extensions and writes a Palm document with encrypted hints and logs: -gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb +gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb diff --git a/xmldoc/formats/psp.xml b/xmldoc/formats/psp.xml index 3407bb16d..b6949d553 100644 --- a/xmldoc/formats/psp.xml +++ b/xmldoc/formats/psp.xml @@ -55,7 +55,7 @@ There are either no points to write, or you have botched the command on the command line. A simple command line to create PSP files looks like this: -gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp +gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp Note the use of "-f" for INPUT files and "-F" for OUTPUT files. diff --git a/xmldoc/formats/stmsdf.xml b/xmldoc/formats/stmsdf.xml index e01b49768..7edbf6ed9 100644 --- a/xmldoc/formats/stmsdf.xml +++ b/xmldoc/formats/stmsdf.xml @@ -15,9 +15,7 @@ 28 = X9 TrackLog - - gpsbabel -i gpx -f some-routes.gpx -r -o stmsdf,index=3 -F single-route.sdf - + gpsbabel -i gpx -f some-routes.gpx -r -o stmsdf,index=3 -F single-route.sdf Suunto Website diff --git a/xmldoc/formats/tef.xml b/xmldoc/formats/tef.xml index 40e5855b2..c8933e809 100644 --- a/xmldoc/formats/tef.xml +++ b/xmldoc/formats/tef.xml @@ -11,5 +11,5 @@ GPSBabel also supports the bcr format, which may also be used with this program and supports both reading and writing. - gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx + gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx diff --git a/xmldoc/formats/text.xml b/xmldoc/formats/text.xml index 1e2952c59..5f8be3037 100644 --- a/xmldoc/formats/text.xml +++ b/xmldoc/formats/text.xml @@ -4,5 +4,5 @@ handy for listings of any type of waypoint files. The following command line reads a GPX file with Groundspeak extensions and writes a text file with encrypted hints: -gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt +gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt diff --git a/xmldoc/formats/wbt-bin.xml b/xmldoc/formats/wbt-bin.xml index f1c49475d..7d57670ad 100644 --- a/xmldoc/formats/wbt-bin.xml +++ b/xmldoc/formats/wbt-bin.xml @@ -6,7 +6,7 @@ by Wintec's Windows application. Command showing conversion of a Wintec binary file to GPX - gpsbabel -i wbt-bin -f tracks.bin -o -gpx -F out.gpx + gpsbabel -i wbt-bin -f tracks.bin -o +gpx -F out.gpx diff --git a/xmldoc/formats/wbt.xml b/xmldoc/formats/wbt.xml index 215f0fea1..834d59af1 100644 --- a/xmldoc/formats/wbt.xml +++ b/xmldoc/formats/wbt.xml @@ -4,6 +4,6 @@ Command showing WBT-200 download and erase over Bluetooth on Mac OS X - gpsbabel -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx + gpsbabel -i wbt,erase -f /dev/cu.WBT200-SPPslave-1 -o gpx -F out.gpx diff --git a/xmldoc/formats/xmapwpt.xml b/xmldoc/formats/xmapwpt.xml index ba949bf00..ff1f2fea3 100644 --- a/xmldoc/formats/xmapwpt.xml +++ b/xmldoc/formats/xmapwpt.xml @@ -31,15 +31,15 @@ It should also be noted that reading multiple files is indeed possible, but if you have more than a few points, it can be a task. For example: -gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt +gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt will read the two Xmap .wpt files and write one mapsend file. This is fine for a small handful of points, but could be quite cumbersome for folks like me who have 100+ waypoints loaded into XMap. For *nix folks, something as simple as: -cat *.wpt > /tmp/foo.wpt -gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt +cat *.wpt > /tmp/foo.wpt +gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt will do the trick just fine. -- 2.30.2